Headless SDK
Hyperswitch is designed to facilitate the integration and management of payment-related functionalities in a decoupled or headless architecture with flexibility to customize your checkout UI.
Last updated
Was this helpful?
Hyperswitch is designed to facilitate the integration and management of payment-related functionalities in a decoupled or headless architecture with flexibility to customize your checkout UI.
Last updated
Was this helpful?
Initialize Hyperswitch Headless SDK onto your app with your publishable key. To get a Publishable Key please find it .
Make a request to the endpoint on your server to create a new Payment. The clientSecret
returned by your endpoint is used to initialize the payment session.
Important: Make sure to never share your API key with your client application as this could potentially compromise your security
Initialize a Payment Session by passing the clientSecret to the initPaymentSession
clientSecret (string)
Required. Required to use as the identifier of the payment.
Using the paymentSession
object, the default customer payment method data can be fetched, using which you can craft your own payments experience. The paymentSession
object also exposes a confirmWithCustomerDefaultPaymentMethod
function, using which you can confirm and handle the payment session.
Payload for confirmWithCustomerDefaultPaymentMethod(payload)
confirmParams (object)
Parameters that will be passed on to the Hyper API.
redirect (string)
(web only) Can be either 'always' or 'if_required'
By default, confirmWithCustomerDefaultPaymentMethod()
will always redirect to your return_url
after a successful confirmation. If you set redirect: "if_required", then this method will only redirect if your user chooses a redirection-based payment method.
ConfirmParams object
return_url(string)
(web only) The url your customer will be directed to after they complete payment.